STM32 Errata Hunter Context

Purpose and scope

The STM32 Errata Hunter Context searches published silicon errata and provides classification and impact analysis for a selected STM32 part and its peripherals. It reports source identifiers and links when available.

The context requires an identifiable full STM32 ordering code. It does not infer applicability from a family name alone.

Context scope

  • errata-hunter.errata-lookup resolves the part number and selected peripherals, then returns matching errata and workarounds.

Assets and capabilities

The context is delivered in the cube-agentic-ai-errata-hunter bundle, which uses a remote service for errata lookup.

The remote service accepts a full ordering code and optional peripheral names, types, or wildcard patterns. The host AI system should cite the errata source when the service provides a document identifier and link.

Cube commands

The bundle command provides context inspection:

:header: “Command”, “Use” :widths: 45, 55

cube cube-agentic-ai-errata-hunter --help

Show the context command help.

cube cube-agentic-ai-errata-hunter --version

Show the installed bundle version.

cube cube-agentic-ai-errata-hunter --list-ai-services

List the errata lookup service.

Errata lookup uses the remote service selected by this context.

Typical prompts

  • Is my current project exposed to known silicon errata? Identify the full STM32 ordering code and configured peripherals first, then cite applicable errata and workarounds.

  • Check the errata that apply to STM32C562RET6 and SPI1.

  • Find silicon limitations for the peripherals configured in this project.

  • Does this STM32 part have an erratum affecting DMA? Cite the errata sheet.

  • List the applicable workarounds and identify the affected peripheral.